<html>

<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<title>OAGIS 8.0 Includes</title>
</head>

<body>

<table border="1" cellpadding="3" cellspacing="0" width="100%">
  <tr>
    <td bgcolor="#FFFF99"><font face="Times New Roman" size="4">
      OAGIS 8.0 Includes</font></td>
  </tr>
</table>
<blockquote>
  <dl>
    <dt><a href="#Same"><font size="3">As in previous releases</font></a></dt>
    <dt><a href="#New Technologies" target="body"><font size="3">New
      Technologies</font></a></dt>
    <dt><a href="#Overlays">Overlaying OAGIS</a></dt>
    <dt><a href="#Documentation"><font size="3">Documentation</font></a></dt>
    <dt><a href="#Scripts"><font size="3">Scripts</font></a></dt>
  </dl>
</blockquote>
<table border="1" cellspacing="0" width="100%" cellpadding="3">
  <tr bgcolor="#e0e0e0" valign="top">
    <td colspan="2">
<p><font size="3"><a name="Same"></a><b>As in previous releases of OAGIS, OAGIS 8.0 includes the&nbsp;</b></font></p>
<ul>
  <li><font size="3">The same content and capabilities as OAGIS Release
    7.2.1.&nbsp;</font>
    <ul>
      <li><font size="3">However with this release, we have taken the
        opportunity to normalize the use of several Nouns and Components through
        out OAGIS.</font></li>
    </ul>
  </li>
  <li><font face="Times New Roman" size="3">A Preface that describes the new
    additions to OAGIS. - This is accessible from the links in the Header above.</font></li>
  <li><font face="Times New Roman" size="3">A description of the OAGIS 8.0
    Business Object Document (BOD) Architecture. - This also is available from
    the links in the Header above.</font></li>
  <li><font face="Times New Roman" size="3">A set of example scenarios, each of
    which describe the chorography or business process that OAGIS maybe used.
    Again, this is an example and by no means limits OAGIS' use. As business
    processes are continually evolved. Often times a companies business process
    is the differentiator between competitors.</font></li>
  <li><font face="Times New Roman" size="3">The Business Object Documents
    themselves, which are available by clicking on the Business Object Documents
    link in the left hand frames.</font></li>
  <li><font face="Times New Roman" size="3">The ability to extend OAGIS through
    the use of the UserArea</font></li>
</ul>
    </td>
  </tr>
</table>
<p>&nbsp;</p>
<table border="1" cellspacing="0" width="100%" cellpadding="3">
  <tr bgcolor="#e0e0e0" valign="top">
    <td colspan="2">
      <p><font size="3"><a name="New Technologies"></a><b>New Technologies</b></font></p>
      <p><font size="3">OAGIS 8.0 also supports additional technologies that
      previous releases did not. These include:</font></p>
      <ul>
        <li><font size="3">Long tag names</font></li>
        <li><font size="3">Updates to the OAGIS terminology. See the <a href="file:///O:/Schema/OAGIS/XML/Schema/Documentation/Architecture/Architecture.htm" target="body">Business
          Object Document Architecture</a> document for these.</font></li>
        <li><font size="3">Take advantage of &quot;core&quot; XML technologies:</font></li>
      </ul>
      <blockquote>
        <ul>
          <li><font face="Times New Roman" size="3">XML Schema</font></li>
          <li><font face="Times New Roman" size="3">XSL and</font></li>
          <li><font face="Times New Roman" size="3">XPath</font></li>
        </ul>
        <p><font face="Times New Roman" size="3">XML Schema is used to capture
        the message structure and type information for the BODs.</font></p>
        <p><font face="Times New Roman" size="3">While XSL and specifically
        XPath is used to capture the required fields and other constraints that
        can be applied to the BODs. XPath is also used to apply the action of
        the Verb on particular Components of the Noun with in the BOD.</font></p>
      </blockquote>
    </td>
  </tr>
</table>
<p>&nbsp;</p>
<table border="1" cellspacing="0" width="100%" cellpadding="3">
  <tr bgcolor="#e0e0e0" valign="top">
    <td colspan="2">
<p><a name="Overlays"></a><b>Overlays</b></p>
<p>By taking advantage of XML Schema and XSL, it is now
possible for industry verticals to take advantage of OAGIS as a horizontal
specification for industry verticals. By providing Overlays that can restrict
the usage of BODs as appropriate for an industry vertical or for that matter for
an given customer's use. Two simple examples of these Overlays are provided with
OAGIS 8.0 in the OverlayExamples directory.&nbsp;</p>
<p>OAGI will provide additional information on how to make use of Overlays in a
white paper that will be posted to the More Information section available from
our Web Site.</p>
    </td>
  </tr>
</table>
<p>&nbsp;</p>
<table border="1" cellspacing="0" width="100%" cellpadding="3">
  <tr bgcolor="#e0e0e0" valign="top">
    <td colspan="2">
<p><font face="Times New Roman"><a name="Scripts"></a><b>Scripts</b></font></p>
<p><font face="Times New Roman">In making use of these &quot;core&quot;
XML Technologies the OAGI XML Team has provided several scripts that have helped
us in the validation of OAGIS 8.0. These are provided &quot;AS IS&quot;. Again
these are scripts for testing and by no means should they be used in a
production environment. To learn more about them please see the <a href="../../Utility/bin/_README.htm" target="body">_readme.htm
</a>file.</font></p>
<p><font face="Times New Roman" size="3">These scripts make use of XML parsers,
XML Schema validators and XSL processors that are freely available from the
Internet. They are provided here in order to help the end-user for the most
recent copy of each please check with specific organization or parties links are
provided in the readme above.</font></p>
    </td>
  </tr>
</table>
<dl>
  <dt>&nbsp;</dt>
</dl>
<table border="1" cellspacing="0" width="100%" cellpadding="3">
  <tr bgcolor="#e0e0e0" valign="top">
    <td colspan="2"><p><font face="Times New Roman"><a name="Documentation"></a><b>Documentation</b></font></p>
<p><font face="Times New Roman">In adding these &quot;core&quot; XML
Technologies, OAGI has been able to move from capturing the documentation (Word,
and PDF formats) and the XML in separate instances to capturing both the
documentation and the XML types and constructs in XML Schema with the
constraints being applied from XSL stylesheets.&nbsp;</font></p>
<p><font face="Times New Roman" size="3"> The html documentation provided
is then generated from this documentation and contains links to the specific XML
Schema, XML Instances, Constraint Rules, and Constraint Stylesheets. This ensures that the documentation
that the business analysis views is the same comments that implementer sees in
the XML Schemas.</font></p>

    </td>
  </tr>
</table>

</body>

</html>
